On the inequality of the 3V's of Big Data Architectural Paradigms: A case for heterogeneity

The well-known 3V architectural paradigm for Big Data introduced by Laney (2011) provides a simplified framework for defining the architecture of a big data platform to be deployed in various scenarios tackling processing of massive datasets. While additional components such as Variability and Veracity have been discussed as an extension to the 3V model, the basic components (Volume, Variety, and Velocity) provide a quantitative framework while variability and veracity target a more qualitative approach. In this paper we argue why the basic 3V’s are not equal due to the different requirements that need to be covered in case there exist higher demands for a particular “V”. We call this paradigm heterogeneity and we provide a taxonomy of the existing tools (as of 2013) covering the Hadoop ecosystem from that perspective. This paper contributes on the understanding of the Hadoop ecosystem from both an architectural and requirements viewpoint and aims to help researchers and practitioners on the design of scalable platforms targeting different business scenarios.